NTISthis.com

Evidence Guide: ICTWEB407 - Conduct operational acceptance tests of websites

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTWEB407 - Conduct operational acceptance tests of websites

What evidence can you provide to prove your understanding of each of the following citeria?

Prepare the test

  1. Establish and document, the testing framework and schedule
  2. Determine the processes and functions to be tested, and assign the quantitative and qualitative performance benchmarks to each process and function
  3. Benchmark and document the page templates, style guides and expected traffic loads
  4. Determine and document the test methodology
  5. Assemble and brief, the testing panel on the conduct of the test
  6. Develop user and installation manuals, according to the target audience’s understanding and needs
Establish and document, the testing framework and schedule

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine the processes and functions to be tested, and assign the quantitative and qualitative performance benchmarks to each process and function

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Benchmark and document the page templates, style guides and expected traffic loads

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine and document the test methodology

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assemble and brief, the testing panel on the conduct of the test

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop user and installation manuals, according to the target audience’s understanding and needs

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test individual pages

  1. Test the pages, against style guides and templates
  2. Test the pages, for consistency in structure and content
  3. Apply the automatic testing software
  4. Document page gross statistics of confirmed results of tests
Test the pages, against style guides and templates

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test the pages, for consistency in structure and content

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Apply the automatic testing software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document page gross statistics of confirmed results of tests

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test page relationships against the business requirements

  1. Test the installation, and the examples listed in instruction manual
  2. Test page navigability using a variety of browsers
  3. Test the ease of use and functionality against the requirements
  4. Test software interface points, against the business and technical requirements
  5. Test site security and privacy against the business requirements
  6. Test the response time against the business requirements
  7. Conduct load simulation testing, using single and multiple independent browsers, or automated load testing tools
Test the installation, and the examples listed in instruction manual

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test page navigability using a variety of browsers

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test the ease of use and functionality against the requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test software interface points, against the business and technical requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test site security and privacy against the business requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test the response time against the business requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Conduct load simulation testing, using single and multiple independent browsers, or automated load testing tools

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Apply and document further tests

  1. 4.1 Test the website's ability to handle concurrent access
  2. Test conformance to the applicable privacy, accessibility, and acceptable usage policy standards
  3. Apply the automatic testing software
  4. Collect, collate and document the results from the sample user, and data from the automated test
4.1 Test the website's ability to handle concurrent access

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test conformance to the applicable privacy, accessibility, and acceptable usage policy standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Apply the automatic testing software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Collect, collate and document the results from the sample user, and data from the automated test

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Evaluate the test results

  1. Consolidate and compare the results to the benchmarks
  2. Identify results that fail to meet the benchmarks, and conduct a site remedial iteration
  3. Record and document the test results as the site performance baseline, against which further development or updating can be measured
  4. Provide evaluation feedback to the appropriate person
  5. Ensure that the appropriate person signs off on the site, prior to the ‘go live’ date
Consolidate and compare the results to the benchmarks

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify results that fail to meet the benchmarks, and conduct a site remedial iteration

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Record and document the test results as the site performance baseline, against which further development or updating can be measured

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Provide evaluation feedback to the appropriate person

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Ensure that the appropriate person signs off on the site, prior to the ‘go live’ date

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prepare the test

1.1 Establish and document, the testing framework and schedule

1.2 Determine the processes and functions to be tested, and assign the quantitative and qualitative performance benchmarks to each process and function

1.3 Benchmark and document the page templates, style guides and expected traffic loads

1.4 Determine and document the test methodology

1.5 Assemble and brief, the testing panel on the conduct of the test

1.6 Develop user and installation manuals, according to the target audience’s understanding and needs

2. Test individual pages

2.1 Test the pages, against style guides and templates

2.2 Test the pages, for consistency in structure and content

2.3 Apply the automatic testing software

2.4 Document page gross statistics of confirmed results of tests

3. Test page relationships against the business requirements

3.1 Test the installation, and the examples listed in instruction manual

3.2 Test page navigability using a variety of browsers

3.3 Test the ease of use and functionality against the requirements

3.4 Test software interface points, against the business and technical requirements

3.5 Test site security and privacy against the business requirements

3.6 Test the response time against the business requirements

3.7 Conduct load simulation testing, using single and multiple independent browsers, or automated load testing tools

4. Apply and document further tests

4.1 Test the website's ability to handle concurrent access

4.2 Test conformance to the applicable privacy, accessibility, and acceptable usage policy standards

4.3 Apply the automatic testing software

4.4 Collect, collate and document the results from the sample user, and data from the automated test

5. Evaluate the test results

5.1 Consolidate and compare the results to the benchmarks

5.2 Identify results that fail to meet the benchmarks, and conduct a site remedial iteration

5.3 Record and document the test results as the site performance baseline, against which further development or updating can be measured

5.4 Provide evaluation feedback to the appropriate person

5.5 Ensure that the appropriate person signs off on the site, prior to the ‘go live’ date

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prepare the test

1.1 Establish and document, the testing framework and schedule

1.2 Determine the processes and functions to be tested, and assign the quantitative and qualitative performance benchmarks to each process and function

1.3 Benchmark and document the page templates, style guides and expected traffic loads

1.4 Determine and document the test methodology

1.5 Assemble and brief, the testing panel on the conduct of the test

1.6 Develop user and installation manuals, according to the target audience’s understanding and needs

2. Test individual pages

2.1 Test the pages, against style guides and templates

2.2 Test the pages, for consistency in structure and content

2.3 Apply the automatic testing software

2.4 Document page gross statistics of confirmed results of tests

3. Test page relationships against the business requirements

3.1 Test the installation, and the examples listed in instruction manual

3.2 Test page navigability using a variety of browsers

3.3 Test the ease of use and functionality against the requirements

3.4 Test software interface points, against the business and technical requirements

3.5 Test site security and privacy against the business requirements

3.6 Test the response time against the business requirements

3.7 Conduct load simulation testing, using single and multiple independent browsers, or automated load testing tools

4. Apply and document further tests

4.1 Test the website's ability to handle concurrent access

4.2 Test conformance to the applicable privacy, accessibility, and acceptable usage policy standards

4.3 Apply the automatic testing software

4.4 Collect, collate and document the results from the sample user, and data from the automated test

5. Evaluate the test results

5.1 Consolidate and compare the results to the benchmarks

5.2 Identify results that fail to meet the benchmarks, and conduct a site remedial iteration

5.3 Record and document the test results as the site performance baseline, against which further development or updating can be measured

5.4 Provide evaluation feedback to the appropriate person

5.5 Ensure that the appropriate person signs off on the site, prior to the ‘go live’ date

Evidence of the ability to:

prepare an operational acceptance test that measures the independent and integrated structural content, and the technical components, of the site

apply automatic testing software and collect, collate and document the results or tests

evaluate and provide feedback on the test results.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

outline the client business domain

describe the structure, function and business organisation of the client, including the business-process design

identify the organisational policies and procedures that cover routine work processes, and the use of:

web optimising tools

web monitoring tools

web testing procedures

describe technical performance measurement

explain website accessibility and equity principles

outline website structures, design and testing methodologies, and standards

describe common website security issues and the methods employed to mitigate risk

list and describe, common testing software and the metrics used

identify and describe, the application of common website testing software.